Verbose garbage collection is not as verbose as the name suggests. 详细垃圾收集并非像其名称暗示的那样详细。
Using garbage collection to simplify memory management for lists. 使用垃圾收集器来简化列表的内存管理。
This approach is preferred when garbage collection for the servant region JVM is reasonable and acceptable. 当服务区域JVM的垃圾收集合理和可接受时,此方法是首选的方法。
Therefore, to use this method of garbage collection, the collector must be integrated with the programming language. 因此,为使用这种垃圾收集方法,垃圾收集器必须与编程语言集成在一起。
The Java heap size and the garbage collection policy are two key factors that affect performance. Java堆大小和垃圾收集策略是影响性能的两大因素。
The LPGC provides garbage collection in parallel to the JVM's work. LPGC提供与JVM的工作并行的垃圾收集功能。
The default value is now false, which changes the method of garbage collection. 现在的默认值是false,这改变了垃圾收集的方法。
The new collectors in JDK1.4.1 are all designed to address the issue of garbage collection on multiprocessor systems. JDK1.4.1中新的收集器都是为解决多处理器系统中垃圾收集器的问题而设计的。
They also describe the garbage collection trace settings. 这些指南还描述了垃圾回收跟踪设置。
Application load, garbage collection concurrency, locality, and allocation efficiencies can all influence application performance. 应用程序负载、垃圾收集并发、位置和分配效率都可能影响应用程序性能。
To understand this, the first thing you need to check is garbage collection. 要理解这一点,首先需要检查的是垃圾收集。
That garbage collection data is also present in any requested Java dump file. 垃圾收集数据也出现在Java转储文件中。
Garbage collection can have a big effect on application performance. 垃圾收集对应用程序的性能具有很大影响。
The tool is useful for diagnosing performance issues, particularly issues related to heap sizing and garbage collection. 该工具有助于诊断性能问题、与堆大小和垃圾收集有关的特殊问题。
Garbage collection can be freeing. It lets us focus on application logic rather than memory management. 垃圾回收解放了我们,它让我们可将精力集中在应用程序逻辑(而不是内存管理)上。
There are several basic strategies for garbage collection: reference counting, mark-sweep, mark-compact, and copying. 有几种垃圾收集的基本策略:引用计数、标记-清除、标记-整理(mark-compact)和复制。
The eden space shows new objects that have never been through garbage collection. Eden空间显示了从未通过垃圾收集的新对象。
This will give you information on the frequency, timing, and duration of garbage collection operations. 这会使您得到垃圾收集操作的频率、定时和持续时间等信息。
Garbage collection is the process of reclaiming invalid blocks ( those that contain some amount of invalid data). 垃圾收集是一个回收无效块的过程(无效块中包含了一些无效数据)。
The first line in the example above indicates a garbage collection occurred. 上面示例中的第一行指示发生了一次垃圾收集。
This creates the best balance between the rate and length of garbage collection cycles. 这样就能够在垃圾回收周期的频率和长度之间实现最佳的平衡。
And finalization adds overhead to instantiation and garbage collection of finalizable objects. 并且终结还为可终结对象的实例化和垃圾收集带来了开销。
The JVM manages its own heap and cleans it through a process known as garbage collection. JVM管理自己的堆并通过垃圾收集过程清理堆。
The Java Virtual Machine now manages garbage collection rather than the system. 现在由Java虚拟机(而不是系统)管理垃圾收集。
Automatic garbage collection is performed on this heap. 自动垃圾回收即是在该堆上执行的。
In this future garbage collection, the objects memory is actually reclaimed. 在后来的垃圾回收中,实际上回收了对象的内存。
Regardless of the algorithm chosen, trends in hardware and software have made garbage collection far more practical. 不管选择什么算法,硬件和软件的发展使垃圾收集更具有实用性。
During the garbage collection process the garbage collector often moves objects to different locations in the heap. 在垃圾收集过程中,垃圾收集器经常吧对象移动到堆中的另外一个位置。
We introduced most of aspects of garbage collection prior to CLR4.0. 以上我们说到了CLR4.0以前垃圾收集的大部分方面。
Only the garbage collection system can destroy an object. 只有垃圾回收系统才能销毁一个对象。